Order configurations
An Order Configuration is a template that defines how a specific order type functions in Mative Cloud LM – Logistics Manager. Every order must reference an Order Configuration, which governs its lifecycle, data fields, and proof-of-delivery requirements.
What an order configuration contains
| Component | Description |
|---|---|
| Name | Display name (e.g., "Standard Delivery", "Cold Chain") |
| Namespace & Key | Unique identifier used by the API (e.g., system:order-config:transport) |
| Description | Internal notes on this configuration's purpose |
| Status | Active or inactive |
| Activity Flow | The ordered sequence of statuses the order moves through |
| Entity Definitions | Custom fields for items (parcels) within the order payload |
| POD Method | How proof of delivery is captured (signature, photo, QR, custom) |
| Custom Fields | Additional order-level fields shown in the console and LM Mobile app |
| Tags | Labels for filtering and organization |
The activity flow
The activity flow defines the exact sequence of statuses a driver must complete in the LM Mobile app. The system includes four static statuses (cannot be removed):
createddispatchedstartedcanceled
All intermediate steps between started and completion are configurable. A step with complete: true closes the order.
Example flow:
created → dispatched → started → enroute → arrived → completed
Cold chain example:
created → dispatched → started → picked_up → in_transit → delivered
The built-in core configuration
Mative Cloud LM – Logistics Manager includes one default configuration:
| Field | Value |
|---|---|
| Name | Transport |
| Namespace | system:order-config:transport |
| Default flow | created → dispatched → started → enroute → completed |
Managing configurations
Navigate to Logistics Manager → Operations → Order Configurations.
Available actions:
- Create new configurations
- Edit existing flows and entity fields
- Duplicate a configuration as a starting point
- Activate/Deactivate availability
- Delete unused configurations
API usage
When creating orders via the API, reference configurations by their public_id:
{
"order_config": "config_dnid32",
"payload": { ... }
}
The API uses public_id values exclusively — internal uuid columns remain database-private.